Risk analysis and fraud detection for electronic transaction processing flows

ABSTRACT

There are provided systems and methods for risk analysis for fraud detection for electronic transaction processing flows. An entity, such as a user, business, or other personal or commercial entity, may interact with another entity in order to engage in a transaction, for example, a purchase, transfer, or other transaction process. The first entity may utilize a service provider to engage in transaction processing, which may provide multiple flows that govern the features provided to the entities. Such features may include fees required for transaction processing. In order to ensure that the entities do not fraudulently choose a flow type that decreases or cancels fees due, or does not provide certain protections to other parties, a risk analysis of the transaction and the account may be executed based on accessible historical data and identifiers. Thus, the entities may automatically be entered to one flow over another based on the risk analysis.

TECHNICAL FIELD

The present application generally relates to risk models for transactionprocessing and more specifically to risk analysis and fraud detectionfor electronic transaction processing flows.

BACKGROUND

Various types of service providers may provide processing services tousers, merchants, other types of businesses, and different entities. Thetypes of processing services may include different flows to theprocessing services, where the different flows govern or provide thetypes of features and processes that the entities may utilize during useof the processing services. For example, one type of processing servicemay provide a flow that allows for free transfer services between knownusers, such as friends and family. In contrast, a transaction processingservice between a customer and a merchant or other business may insteadrequire a fee paid by one of the parties, but may also provide consumerprotection to the customer and/or fraud protection to the merchant.However, in order to avoid these fees or other undesirable processingservice features for a particular flow, one or more of the entities maydefraud the service provider by selecting an incorrect flow. Thus, theservice provider may lose valuable business and may provide inadequateservices or be at risk of non-compliance with required laws, legalguidelines, and/or merchant/company policy. Moreover, where one of theentities is less savvy than the other entity during use of theprocessing service(s) of the service provider, the other entity may takeadvantage of the first entity by requesting that they enter into aprocessing service flow that is disadvantageous to the first entity andmore preferable to the other entity, for example, to avoid fees requiredby a merchant while not providing consumer protection support to thefirst entity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2A is an exemplary selection interface for choosing a particulartransaction processing flow type for use in transaction processing,according to an embodiment;

FIG. 2B is an exemplary transaction processing interface for entry oftransaction information used in a risk analysis of selection of aparticular transaction processing flow type, according to an embodiment;

FIG. 2C is an exemplary transaction processing interface after entry ofinput to the transaction processing flow, according to an embodiment;

FIG. 3 is an exemplary system environment showing a database of aservice provider having data used to provide risk analysis and frauddetection during transaction processing, according to an embodiment;

FIG. 4 is a flowchart of an exemplary process for risk analysis andfraud detection for electronic transaction processing flows, accordingto an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for risk analysis and fraud detection forelectronic transaction processing flows. Systems suitable for practicingmethods of the present disclosure are also provided.

One or more entities, such as personal users or consumers, groups ofusers, merchants, businesses, or other commercial or governmentalagencies, may wish to engage in electronic transaction processing withone or more other entities. For example, a first entity may wish toprovide a payment to a second entity for a transaction, such as apurchase of one or more items, a bill payment, or other type of requiredpayment or transfer of money between two parties interacting to conductbusiness or engage in a commercial transaction. In other embodiments,the first entity may wish to conduct a personal transaction, such as atransfer between known entities (e.g., friends and/or family memberstransferring money) or a payment between friends (e.g., forreimbursement for borrowed money, a portion of a bill, etc.). Variousservice providers may provide transaction processing services that mayallow two or more entities to engage in transaction processing for atransaction. For example, a payment provider service may offertransaction processing services that provide transfers, paymentservices, reimbursement or refund services, and other type of financialservices including payment account establishment and/or management.These service providers may further provide additional types ofbenefits, features, and/or processes to users, such as buyer/consumerprotection, payment/transfer insurance, fraud protection andreimbursement guarantees, and other types of services that may beoffered for free depending on the transaction processing service and/orentity status, or purchased through payment of a fee (where the fee maybe dependent on the transaction cost or a flat fee based on thetransaction, service, etc.).

In this regard, a service provider may provide multiple differenttransaction processing flow types for transaction processing. Forexample, a transaction processing flow may correspond to the normal ordefault procedure and processes, executable by the service provider, toprovide transaction processing services to entities in a transaction.Each of the transaction processing flow types, models, or procedures maydetermine the processes and features available to the entities engagingin the transaction that is processed using the selected transactionprocessing flow type. Thus, transaction processing flow types maydetermine the fees applicable to one or more of the entities, theprotections available to the entities as a result of transactionprocessing and/or payment, and other types of transaction processingservices available to the entities as a result of utilizing atransaction processing flow type to process the transaction between theentities. One type of transaction processing flow may be available tofriends, family, or other known acquaintances that allows for processingof a transfer, purchase payment, or other type of financial transactionbetween two or more entities that are known to each other. In thisregard, the “friends and family” or personal type of transactionprocessing flows may not require a fee for use of the transactionprocessing flow services of the service provider but may also notprovide consumer protection, such as reimbursement protection andprocesses, refund processes, and/or fraud protection. In contrast, amerchant or consumer type of transaction processing flow may require thebuyer and/or seller in a transaction to pay a fee for use of thetransaction processing flow and to process the transaction, but mayfurther provide other services including the aforementioned consumerprotection services.

The entities may further be required to establish an account with theservice provider in order to engage in transaction processing andutilize one or more types of transaction processing flows. The entitiesmay be required to provide entity information to establish the account,such as personal information for a user, business or merchantinformation for such an entity, or other types of identificationinformation including a name, address, and/or other information. Theentities may also be required to provide financial information,including payment cards (e.g., credit/debit cards), bank accountinformation, gift cards, and/or benefits/incentives. In order to createan account, each entity may be required to select an account name and/orprovide authentication credentials, such as a password, personalidentification number (PIN), answers to security questions, and/or otherauthentication information. Once an account is created, the account maybe accessed through a web browser from a website of the service providerand/or a dedicated application of the service provider, such as a mobilesmart phone application. The entities may engage in transactionprocessing through accessing their respective accounts and providingtransaction information for the transaction. Moreover, a token may beissued to the entity for their respective account, where the token mayinclude data (which may be encrypted) allowing the service provider toidentify the entity and their account and authenticate the entity. Thus,the token may be transmitted to other entities during transactionprocessing, which may allow the service to identify and authenticate theentity's account and engage in transaction processing. Additionally, theonline payment provider or other service provider may provide digitalwallet services, which may offer financial services to send, store, andreceive money, process financial instruments, and/or provide transactionhistories. Thus, the accounts may store information associated with eachentity, which may be utilized to determine a type of transaction engagedin by the entity and/or a type of transaction processing flow requiredby the entity.

In this regard, a computing device on an entity may further include amobile payment application or more generally a transaction processingapplication, which may be configured to send and receive payments toanother party, such as another user and/or a merchant, or otherwiseengage in transaction processing. In various embodiments, a website mayprovide the transaction processing services, and thus may be accessed bya web browser application. The application (or website) may beassociated with a payment provider, such as PayPal® or other onlinepayment provider service, which may provide payments and the otheraforementioned transaction processing services on behalf of user,merchants, and other entities. The application may execute on thecomputing device for a user or a merchant, and may provide variousfunctionalities and processes to the user and/or merchant. For example,a user may utilize the application to send and/or receive paymentsbetween the user and another user/merchant. The user may wish to providea payment for a transaction with a user/merchant, transfer money toanother family/friend, engage in a transaction previously generated andprovided to the payment application, initiate a transaction with anotherentity, or perform another process. The merchant may similarly sendand/or receive payments between the merchant and another user/merchant,which may include receiving payment for transactions, providing paymentsto employees and/or for business expenses, transfer money betweenaccounts, or perform further transaction processing. Other entities,such as charitable organizations and businesses may also utilize theapplication, for example, to receive donations from various partiesand/or pay business expenses.

Thus, the service provider may receive transaction information duringtransaction processing, which may correspond to entities in atransaction (e.g., an entity name, identifier, and/or token, such as atoken used to identify an account of the entity), items in atransaction, transaction cost, tax, tip, shipping information, a messageto an entity in the transaction and/or messages between the entities,and other types of transaction information. The transaction informationmay be generated from a transaction between the entities, and may beprovided to the service provider for processing through selection of atype of a transaction processing flow by the service provider. Thetransaction information may indicate the type of transaction, such as atransaction between a business or merchant and a user or between twousers for personal reasons. The transaction information may include aninitial selection of a transaction processing flow type, such as apersonal transaction and request for a personal transaction processingflow or a commercial transaction and request for a commercialtransaction processing flow. The transaction processing flow may beselected by one or more of the entities in the transaction, for example,on request for transaction processing by the service provider and/orduring entry of the transaction information.

However, in other embodiments, neither entity may select the type oftransaction processing flow, where selection and/or advisement ofselection of the transaction processing flow type may be performed bythe service provider. The transaction information may be used todetermine a type of transaction, such as a personal transaction,commercial transaction, or other transaction. Thus, the service providermay determine the appropriate transaction processing flow type dependingon the transaction information and the type of transaction that requiresa particular flow, the entities information and/or accounts, and/orflags of the entities and/or transaction as potentially abusive of anincorrect type of transaction processing flow, as discussed herein.

Utilizing the transaction information, such as identificationinformation of the entities (e.g., an identifier, account information,and/or token for each entity), the service provider may access orretrieve account information for an account for each entity. The accountinformation for the entity may include information that may be utilizedto further determine a type of transaction that an entity is engaging inwith another entity. For example, if the entity is marked as a merchantin the account information, the entity may be more likely to be engagingin a business or commercial transaction, such as selling an item to aconsumer. In contrast, an account for an individual user may be utilizedfor personal transactions, such as rent payments to a roommate,transfers to a family member, or other type of personal transaction. Theaccount information may therefore include the aforementioned entityinformation and/or financial information for each entity in thetransaction. Additionally, the account information may include previoustransactions in a transaction history, which may include transactiontypes engaged in by the entity with the same entity in the transactionand/or other entities, as well as used transaction processing flow typeswith the same entity and/or other entities.

In further embodiments, the account information may include accountflags that identify the account as engaging in particular types oftransactions and/or utilizing certain transaction processing flow types.For example, where the account is utilized solely with another account(e.g., to transfer money where a merchant may utilize multiple accountsand/or two family members may transfer money), the account of the entitymay be utilized for personal transaction types or transaction processingflows that do not require consumer protection. However, where theaccount engages with multiple other entities, the account informationmay indicate that the entity is engaging in a commercial transactionrequiring a fee and consumer protections. Moreover, an account thatpreviously attempts to use or uses one type of transaction processingflow, such as a personal transaction processing flow that does notrequire a fee for use but provides no consumer protection, but theaccount fraudulently uses the type of the transaction processing flow(e.g., is reported or it is determined the entity for the accountengaged in a different type of transaction require a different type oftransaction processing flow), the account may be flagged as abusive andthat the account should be using another type of transaction processingflow

Thus, the service provider may determine a transaction type for thetransaction engaged in between the entities using the transactioninformation and/or the account information. For example, the transactioninformation may include one or more items for sale to the other entity,which may indicate that the transaction is a commercial transaction. Amessage field may include a message, which may indicate the transactiontype and/or the required transaction processing flow type throughrecognition of characters, words, and/or phrases in the message (e.g.,“ship items to X” may indicate a commercial transaction, while “rent” or“refund” may indicate a transaction not requiring a fee). Thus, thetransaction type may be determined based on a transaction amount, anitem in the transaction, an address for the transaction, an accounthistory for each entities account, and/or a message associated with thetransaction. The transaction type may also be determined using insteador also using the account information, such as an indication of theentities purpose or use of the account, as well as flags for theaccount. Once a transaction type is determined, the service provider maydetermine a required or suggested transaction processing flow type, suchas a transaction processing flow for personal transactions without a feebut between trusted users that do not require consumer protection or atransaction processing flow for commercial transactions requiring a feebut providing consumer protection between unknown parties or parties indanger of fraud.

Based on the type of transaction processing flow required or suggestedfor the transaction type of the transaction between the entities, anoption may be automatically selected by the service provider duringtransaction processing. The option may be selected by automaticallyentering input into the transaction processing flow that selects thetype of the transaction processing flow and/or the features, processes,and/or services provided for transaction processing of the transactionthrough the selected type of the transaction processing flow. Forexample, input may be entered prior to or during selection of atransaction processing flow type that selects one of the transactionprocessing flow types, such as a personal or “friends and family”transaction processing flow that does not require a fee but does notprovide consumer protection, or a consumer or “goods and services”transaction processing flow that requires a seller or merchant to pay afee but provides consumer protection. The transaction processing flowtype may be selected through entry of input to an interface optionoutput to a user through a graphical user interface of an application,such as an interface of a webpage for a website of the service provider(e.g., visible in a browser application) or an interface of a dedicatedmobile application. The input may correspond to checking a box for atransaction processing flow type, selecting a drop down menu, orentering text to the interface. The interface option for the transactionprocessing flow type may be selected in the interface for the entityrequesting transaction processing, for example, the entity requesting apayment to another entity, such as a buyer in a transaction or a partyrequesting to transfer money to another party. In other embodiments, theinterface option may be selected through the input provided to thereceiving entity for the payment or transfer, for example, by the selleror receiving party for the transfer.

Moreover, the input may further be able to be edited by one or more ofthe entities in order to change to transaction processing flow type. Forexample, where a box may be checked to enter the consumer or goods andservices flow requiring a fee for transaction processing, one or more ofthe entities may change the transaction processing flow type byunchecking the box or otherwise entering input. When an entity changesthe type of the transaction processing flow, information, such as analert, may display in an interface that informs the entity of theprocesses, features, and/or services of the originally required orsuggested transaction processing flow type and/or the newly selectedtransaction processing flow type (through the change input by theentity). For example, the displayed information may inform the user ofthe change in fees, consumer protection, insurance, reimbursement orrefund policies, and/or other features that change, were previouslyselected, and/or are now selected from the transaction processing flowtype. The entity changing the transaction processing flow type may berequired to confirm reading the information and/or the requested changein the transaction processing flow type.

Thus, the service provider may then process the transaction using theselected transaction processing flow type. As a result of processing thetransaction using the selected transaction processing flow type, one ormore of the entities may be required to pay a fee (which may be added toor deducted from a payment for the transaction or requested from anentity). Additionally, one or more of the entities may receive benefitsand other services as a result of the transaction processing flow type,such as consumer and/or fraud protection services, which may be utilizedwith the service provider. Other types of the services and/or featuresmay also be provided to the entities. A transaction history may record areceipt or other history of the transaction, which may be utilized toprovide goods, services, and/or products (referred to herein as an“item” or “items”) to an entity in the transaction. Moreover, a paymentmay be provided by deducting an amount from one entity's account andcrediting the amount (which may have deducted a fee) to the account ofthe other entity.

The service provider may determine whether one or more of the entitiesbehaved abusively by selecting an incorrect transaction processing flowtype. For example, the service provider may flag an entity and/oraccount for the entity as abusive or potentially abusive if the entityattempts to enter or select an incorrect transaction processing flow forthe transaction type engaged in by the entity. In further embodiments,if the entity changes the transaction type automatically preselected bythe service provider, to another transaction processing flow type thatdoes not appear to match the transaction type, the service provider mayflag the entity as abusive or potentially abusive. Moreover,post-transaction processing reports and/or analysis may be utilized todetermine if the entity is abusing or potentially abusing an incorrecttransaction processing flow type, for example, to avoid transactionprocessing fees. Post-transaction processing reports may includerequests for consumer protection, fraud reports and protection,reimbursement for a transaction, or other types of requests or reportsthat correspond to a commercial or sales transaction. Such reportsresulting from a transaction processed using a personal transactionprocessing flow type that does not provide such protections may beutilized to determine that the buyer entity or seller entity actedabusively, for example, to avoid a fee, and may therefore be used toflag an account or entity as abusive. Thus, during future transactionprocessing, the flag of the entity or account of the entity as abusivemay be used to automatically select the transaction processing flow typerequired by the entity during transaction processing. In this regard, ifthe entity is flagged as abusing a free personal or “friends and family”transaction processing flow type to avoid a fee but not provide consumerprotection during sales to other entities, the commercial or “goods andsales” transaction processing flow type may automatically be selectedfor all transaction processing engaged in by the flagged entity.

Moreover, in certain embodiments, an entity and/or account for an entitythat continues to abuse an incorrect transaction processing flow typemay be blacklisted or may be forced to utilize (e.g., not allowed tochange) a particular transaction processing flow type. In suchembodiments, the entity may be able to change the transaction processingflow type through personal correspondence and provision of additionalinformation to the service provider.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a communication device 110, a merchant device 120,and a transaction processor server 130 in communication over a network150. The user or other entity (not shown) may utilize communicationdevice 110 to utilize the various features available for communicationdevice 110, which may include processes and/or applications associatedwith transaction processing for a transaction between the user and amerchant or other entity (not shown) associated with merchant device120. During transaction processing of the transaction, the user and/orthe merchant may utilize communication device 110 and/or merchant device120, respectively, to engage in a type of a transaction processing flowused to process the transaction. Transaction processor server 130 mayautomatically select the transaction processing flow type based onreceived transaction information for the transaction between the userand the merchant. Additionally, the user and the merchant may utilizecommunication device 110 and/or merchant device 120, respectively, toestablish accounts with transaction processor server 130, where accountinformation for the accounts may further be utilized to select atransaction processing flow type for processing the transaction. Forexample, the accounts may include account flags where the user and/orthe merchant may have previously engaged in abusive behavior byselecting or attempting to select an incorrect transaction processingflow type.

Communication device 110, merchant device 120, and transaction processorserver 130 may each include one or more processors, memories, and otherappropriate components for executing instructions such as program codeand/or data stored on one or more computer readable mediums to implementthe various applications, data, and steps described herein. For example,such instructions may be stored in one or more computer readable mediasuch as memories or data storage devices internal and/or external tovarious components of system 100, and/or accessible over network 150.

Communication device 110 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with merchant device 120, and/ortransaction processor server 130. For example, in one embodiment,communication device 110 may be implemented as a personal computer (PC),telephonic device, a smart phone, laptop/tablet computer, wristwatchwith appropriate computer hardware resources, eyeglasses withappropriate computer hardware (e.g. GOOGLE GLASS®), other type ofwearable computing device, implantable communication devices, and/orother types of computing devices capable of transmitting and/orreceiving data, such as an IPAD® from APPLE®. Although only onecommunication device is shown, a plurality of communication devices mayfunction similarly.

Communication device 110 of FIG. 1 contains a service providerapplication 112, other applications 114, a database 116, and acommunication module 118. Service provider application 112 and otherapplications 114 may correspond to executable processes, procedures,and/or applications with associated hardware. In other embodiments,communication device 110 may include additional or different moduleshaving specialized hardware and/or software as required.

Service provider application 112 may correspond to one or more processesto execute software modules and associated devices of communicationdevice 110 to enter one or more payment instruments or other fundingsources for storage in a digital wallet associated with a paymentaccount (e.g., stored and/or serviced by transaction processor server130), access the digital wallet and/or payment account for use, andengage in transaction processing with another entity through transactionand payment processing using a transaction processing flow having aspecific type, where the specific type may be suggested and/orautomatically selected by transaction processor server 130. In thisregard, service provider application 112 may correspond to specializedhardware and/or software utilized by a user of communication device 110that provides an interface to permit the user to enter input and otherdata for payment instruments, for example, through an input device(e.g., touch screen with a graphical user interface, keypad/keyboard,mouse, etc.) and/or through a data capture device (e.g., scanner,camera, other optical device, etc.) Such information may be stored withtransaction processor server 130 for use with an online digital walletand/or account for the user, which may be utilized for transactionprocessing with another entity, such as a merchant associated withmerchant device 120.

In various embodiments, information for the account may also be storedto communication device 110 for use in an offline environment. Theaccount accessible through service provider application 112 may be usedto initiate, receive, and/or process/complete transactions usingservices provided by transaction processor server 130. Once entered, thepayment instruments may be communicated to transaction processor server130 over network 150 by service provider application 112 forestablishment and/or maintenance/update of the account and/or entry intothe digital wallet for the user. The user of communication device 110may also enter benefits to service provider application 112. Thebenefits may correspond to one or more of rewards programs, rewardsprograms membership level, rewards program points, available items in atleast one rewards program, cash-back amounts for the at least onerewards program, airline miles, promotional credit, promotional creditrates, promotional discount rate, merchant discounts, merchant discountrates, and merchant coupons.

Service provider application 112 may utilize one or more userinterfaces, such as graphical user interfaces presented using an outputdisplay device of communication device 110, to enable the userassociated with communication device 110 to select and provide payment.In various embodiments, service provider application 112 may correspondto a general browser application configured to retrieve, present, andcommunicate information over the Internet (e.g., utilize resources onthe World Wide Web) or a private network. For example, service providerapplication 112 may provide a web browser, which may send and receiveinformation over network 150, including retrieving website information(e.g., a website for transaction processor server 130), presenting thewebsite information to the user, and/or communicating information to thewebsite, including payment information for transaction processed throughtransaction processor server 130.

However, in other embodiments, service provider application 112 mayinclude a dedicated application of transaction processor server 130 orother entity (e.g., a merchant), which may be configured to assist inprocessing transactions. The interface(s) providing by service providerapplication 112 may be utilized to engage in a transaction processingflow having a particular type for a transaction type engaged in by theuser associated with communication device 110. In this regard, input maybe automatically entered to a transaction processing flow in order toselect a type for the transaction processing flow and/or the servicesand/or features of the transaction processing flow. The input may beautomatically entered and displayed to the user through service providerapplication 112 by transaction processor server 130, as discussedherein. However, service provider application 112 may further allow forthe user to change the transaction processing flow type through furtherinput, which may affect the services and features provided bytransaction processor server 130 for processing the transaction, asdiscussed herein. Moreover, service provider application 112 may beutilized to view any account flags for abusive or potentially abusiveuse of an incorrect transaction processing flow.

Service provider application 112 may be utilized to select paymentinstrument(s) for use in providing payment for a purchase transaction,transfer, or other financial process. As discussed herein, serviceprovider application 112 may utilize user financial information, such asa credit card, bank account, or other financial account, as a paymentinstrument when providing payment information. Additionally, serviceprovider application 112 may utilize a digital wallet stored with anaccount with a payment provider, such as transaction processor server130, as the payment instrument, for example, through providing a tokenthat identifies the account and authenticates the user for use of theaccount. Selection of a payment instrument may occur prior to, at, orafter establishment of the financial process. Transaction processorserver 130 may then use the payment instrument during processing ofpayment, as discussed herein with respect to transaction processorserver 130.

Service provider application 112 may be utilized to view the results ofpayment, for example, using transaction histories, dispute resolutionprocesses, and other post-transaction process. Service providerapplication 112 may also store and/or utilize a digital token for thepayment account, digital wallet, and/or payment instruments of the user.Thus, service provider application 112 may provide the digital token toauthenticate the user and/or use the user's payment account, digitalwallet, and/or payment instruments. Service provider application 112 mayuse such a token during transaction processing to authenticate the userand complete transaction processing by providing the token, which may beencrypted and/or provided through a secure channel, to a transactionparticipant to authenticate the user and/or the user's payment account,digital wallet, and/or payment instruments to transaction processorserver 130 and allow for transaction processing and payment using theuser's payment account, digital wallet, and/or payment instruments.

In various embodiments, communication device 110 includes otherapplications 114 as may be desired in particular embodiments to providefeatures to communication device 110. For example, other applications114 may include security applications for implementing client-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 150,or other types of applications. Other applications 114 may also includeemail, texting, voice and IM applications that allow a user to send andreceive emails, calls, texts, and other notifications through network150. In various embodiments, other applications 114 may includefinancial applications, such as banking applications. Other applications114 may also include other location detection applications, which may beused to determine a location for the user, such as a mapping, compass,and/or GPS application, which can include a specialized GPS receiverthat obtains location information for communication device 110 andprocesses the location information to determine a location ofcommunication device 110 and the user. Other applications may includesocial networking applications, media viewing, and/or merchantapplications. Other applications 114 may include device interfaceapplications and other display modules that may receive input from theuser and/or output information to the user. For example, otherapplications 114 may contain software programs, executable by aprocessor, including a graphical user interface (GUI) configured toprovide an interface to the user. Other applications 114 may thereforeuse devices of communication device 110, such as display devices capableof displaying information to users and other output devices, includingspeakers.

Communication device 110 may further include database 116 stored to atransitory and/or non-transitory memory of communication device 110,which may store various applications and data and be utilized duringexecution of various modules of communication device 110. Thus, database116 may include, for example, identifiers such as operating systemregistry entries, cookies associated with service provider application112 and/or other applications 114, identifiers associated with hardwareof communication device 110, or other appropriate identifiers, such asidentifiers used for payment/user/device authentication oridentification, which may be communicated as identifying communicationdevice 110 to transaction processor server 130. Database 116 may includewebpage and/or application information for a transaction processing flowtype, as well as received transaction information for processing atransaction using the transaction processing flow type. In variousembodiments, account information and/or digital wallet information maybe stored to database 116 for use by communication device 110,

Communication device 110 includes at least one communication module 118adapted to communicate with merchant device 120 and/or transactionprocessor server 130. In various embodiments, communication module 118may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency, infrared, Bluetooth, and near field communication devices.Communication module 118 may communicate directly with nearby devicesusing short range communications, such as Bluetooth Low Energy, LTEDirect, WiFi, radio frequency, infrared, Bluetooth, and near fieldcommunications.

Merchant device 120 may be implemented using any appropriate hardwareand software configured for wired and/or wireless communication withcommunication device 110 and/or transaction processor server 130.Although described below as a device, merchant device 120 may correspondto a device, server, or cloud computing architecture to provide sales ofitems, for example, through an online marketplace accessible over anetwork connection with merchant device 120 and/or a physical merchantlocation. Merchant device 120 may further be used to process paymentsfor items and provide incentives for purchase of items and/oradvertisement of items to other users. Although a merchant device isshown, the merchant device may be managed or controlled by any suitableprocessing device. Although only one merchant device is shown, aplurality of merchant devices may function similarly.

Merchant device 120 of FIG. 1 contains a sales application 122, otherapplications 124, a database 126, and a communication module 128. Salesapplication 122 and other applications 124 may correspond to processes,procedures, and/or applications executable by a hardware processor, forexample, a software program. In other embodiments, merchant device 120may include additional or different modules having specialized hardwareand/or software as required.

Sales application 122 may correspond to one or more processes to executemodules and associated specialized hardware of merchant device 120 thatprovides an interface and/or online marketplace to sell one or moreitems offered by a merchant (not shown) associated with merchant device120, and further provide checkout and payment processes for atransaction to purchase the items for sale from the merchantcorresponding to merchant device 120, where such transaction processingservices may be provided through transaction processor server 130. Inthis regard, sales application 122 may correspond to specializedhardware and/or software of merchant device 120 to provide a convenientinterface to permit a merchant to offer items for sale. For example,sales application 122 may be implemented as an application offeringitems for sale that may be utilized by the merchant or a merchantemployee to enter items selected by a user to a transaction, determine aprice for the transaction, and initiate a checkout and payment processfor the transaction. In other embodiments, sales application 122 may beaccessed by communication device 110 to select the items for sale to theuser associated with communication device 110.

In certain embodiments, sales application 122 may correspond to awebsite available over the Internet and/or online content and/ordatabase information accessible through a dedicated application. Thus,sales application 122 may provide item sales through an onlinemarketplace using the website of the merchant. However, in otherembodiments, merchant device 120 may be local to a physical merchantlocation and provide transaction processing processes through interfacesdisplayed to a merchant or merchant employee at the merchant location.Sales application 122 may include information for a price for the item,a discount for the item, a price change for the item, and/or otherincentives for items and/or with the merchant corresponding to merchantdevice 120 (e.g., rebates, payments, etc.). Sales application 122 may beused to set and/or determine a benefit or incentive provided to a userof communication device 110. The sales data and other item data may beretrievable by communication device 110 and/or transaction processorserver 130, such as requestable through an API call, retrievable from adatabase, and/or scraped from an online resource.

Sales application 122 may be used to establish a transaction once theuser associated with communication device 110 has selected one or moreitems for purchase. Once a payment amount is determined for thetransaction for the item(s) to be purchased, sales application 122 mayrequest payment from the user through a transaction processing flowprovided by transaction processor server 130. Sales application 122 mayreceive payment processing information. In such embodiments, thetransaction may be processed using a transaction processing flow havinga particular type provided by transaction processing server 130. Thus,payment provided to the merchant account, and notification of payment(or failure, for example, where there are insufficient user funds) maybe sent to sales application 122. The payment may be made by transactionprocessor server 130 on behalf of the user associated with communicationdevice 110. In other embodiments, sales application 122 may direct theuser to one or more interfaces provided by transaction processor server130 for transaction processing, where transaction information may bepopulated to a transaction processing flow for selection of thetransaction processing flow type and processing of the transaction.

Thus, sales application 122 may include one or more interfaces to engagein a transaction processing flow having a particular type for atransaction type of the transaction. In this regard, input may beautomatically entered to a transaction processing flow in order toselect a type for the transaction processing flow and/or the servicesand/or features of the transaction processing flow. The input may beautomatically entered and displayed to the user through salesapplication 122 by transaction processor server 130, as discussedherein. In other embodiments, the merchant may not view the transactionprocessing, which may be performed by the user associated withcommunication device 110. Additionally, sales application 122 mayfurther allow for the merchant to change the transaction processing flowtype through further input, which may affect the services and featuresprovided by transaction processor server 130 for processing thetransaction, as discussed herein. Moreover, sales application 122 may beutilized to view any account flags for abusive or potentially abusiveuse of an incorrect transaction processing flow. Sales application 122may then receive the results of the transaction processing, and completethe transaction with the user, for example, by providing the user theitems for the transaction or declining the transaction where the user isnot authenticated or the transaction is not authorized (e.g.,insufficient funds).

Merchant device 120 includes other applications 124 as may be desired inparticular embodiments to provide features to merchant device 120. Forexample, other applications 124 may include security applications forimplementing server-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 150, or other types of applications.Other applications 124 may also include email, texting, voice and IMapplications that allow a user to send and receive emails, calls, texts,and other notifications through network 150. In various embodiments,other applications 124 may include financial applications, such asbanking, online payments, money transfer, or other applicationsassociated with transaction processor server 130. Other applications 124may contain software programs, executable by a processor, including agraphical user interface (GUI) configured to provide an interface to theuser.

Merchant device 120 may further include database 126 which may include,for example, identifiers such as operating system registry entries,cookies associated with sales application 122 and/or other applications124, identifiers associated with hardware of merchant device 120, orother appropriate identifiers, such as identifiers used forpayment/user/device authentication or identification. Identifiers indatabase 126 may be used by a payment/credit provider, such astransaction processor server 130, to associate merchant device 120 witha particular account maintained by the payment/credit provider. Item,sales, and/or benefit information for items sold by the merchantassociated with merchant device 120 may be stored to database 126.Database 126 may further include transaction information and/or results,including transaction histories.

Merchant device 120 includes at least one communication module 128adapted to communicate with communication device 110 and/or transactionprocessor server 130. In various embodiments, communication module 128may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency, infrared, Bluetooth, and near field communication devices.

Transaction processor server 130 may be maintained, for example, by anonline service provider, which may provide transaction processingservices on behalf of users and/or merchants. In this regard,transaction processor server 130 includes one or more processingapplications which may be configured to interact with communicationdevice 110, merchant device 150, and/or another device/server tofacilitate transaction processing. In one example, transaction processorserver 130 may be provided by PAYPAL®, Inc. of San Jose, Calif., USA.However, in other embodiments, transaction processor server 130 may bemaintained by or include another type of service provider, which mayprovide connection services to a plurality of users.

Transaction processor server 130 of FIG. 1 includes a fraud analysisapplication 140, a transaction processing application 132, otherapplications 134, a database 136, and a network interface component 138.Transaction processing application 132 and other applications 134 maycorrespond to executable processes, procedures, and/or applications withassociated hardware. In other embodiments, transaction processor server130 may include additional or different modules having specializedhardware and/or software as required.

Fraud analysis application 140 may correspond to one or more processesto execute software modules and associated specialized hardware oftransaction processor server 130 to analyze transaction and accountinformation for a transaction and entities involved in the transactionto determine a transaction type and a required transaction processingflow type for processing the transaction type, as well as determine arisk that the entities are acting fraudulently by attempting to utilizean incorrect transaction processing flow type. In this regard, fraudanalysis application 140 may correspond to specialized hardware and/orsoftware to receive transaction information and/or access accountinformation for determination of whether entities in a transaction areacting fraudulently by selecting an incorrect transaction processingflow type and/or automatically select a transaction processing flow typedepending on the received information. For example, transactioninformation for a transaction may correspond to the name or otheridentifier for entities in the transaction, items involved in thetransaction (e.g., sold to one or more entities), a cost of thetransaction, additional costs (e.g., tax, tip, etc.), a message for thetransaction (e.g., a shipping address, note to customer, iteminformation, etc.), shipping information, and/or other information forthe transaction.

Based on the transaction information, fraud analysis application 140 maydetermine whether the transaction is personal or between knownacquaintances that does not require consumer protection (e.g., fraudprotection, refund services, etc.), whether the transaction iscommercial or between buyers and sellers that requires a fee fortransaction processing and provides consumer protection, or whether thetransaction is another type of transaction requiring different servicesto process through another type of transaction processing flow types.For example, a message field may be analyzed for key words to determinea commercial transaction, or items sold and a cost of the transactionmay indicate a commercial transaction.

Account information may also be utilized by fraud analysis application140 to determine a transaction type for the transaction information. Theaccount information may include entity information in the account,financial information, past transactions using the account, accountpurpose and use, and other accounts interacting with the account. Inthis regard, an account for a named merchant may be utilized todetermine that the transaction type is commercial instead of personalfor a transaction with a previously unknown user. Similarly, pasttransactions may be compared between the entities, such as two usersthat may transfer the same amount of money monthly (e.g., for rent) ortwo unknown entities performing a one-time transaction similar to othersales transactions in the past by one of the entities. Moreover, thenumber of interacting accounts may indicate a transaction type, such asmultiple transactions with different accounts a day being more likely tobe commercial transactions, while transactions with a single otheraccount likely to be personal transfers between known users or the sameuser. Additionally, it may be detected whether the accounts are linkedor share an entity identifier, such as the same name, address, financialinformation, or other information, in order to determine whether thetransaction is personal or commercial in nature. Moreover, previouslyestablished account flags that flag an account as previously havingacted fraudulently by selecting and/or utilizing an incorrecttransaction processing flow may be utilized to select a correcttransaction processing flow, for example, by flagging the account asutilizing a personal transaction processing flow to avoid a fee wherethe account should have used a commercial flow for a previoustransaction.

Thus, fraud analysis application 140 may determine transaction type.Based on the transaction type, fraud analysis application 140 maydetermine a type of transaction processing flow required by the entitiesor appropriate/designated for processing the transaction. Where atransaction processing flow type has not yet been selected by theentities, fraud analysis application 140 may automatically enter inputduring transaction processing of the transaction between the entities toselect a correct transaction processing flow type associated with thetransaction type. Such input may be entered during transactionprocessing using transaction processing application 132. Additionally,transaction processing application 132 may allow the entities, such asthe user or the merchant, to change the transaction processing flowtype, where fraud analysis application 140 may output informationalerting the user and/or the merchant of the change to the transactionprocessing flow type, and the resulting changes in services and/orfeatures from the change. Fraud analysis application 140 may requireconfirmation from the user and/or the merchant for the change, and mayfurther analyze the change and whether the user and/or the merchant haveacted fraudulently by making the change, for example, based on thesuggested and/or selected transaction processing flow type for thedetermined transaction type.

Additionally, in order to determine whether the entities (e.g., the userand/or the merchant) are acting fraudulently, fraud analysis application140 may determine whether one or more of the entities selected theincorrect transaction processing flow type and/or requested a change toan incorrect transaction processing flow types, for example, the avoidpayment of a fee by utilizing a personal transaction processing flowthat does not afford the user consumer protection with the merchant.Fraud analysis application may compare the determined transactionprocessing flow type for the transaction type to a transactionprocessing flow type selected by the user and/or merchant, or changed bythe user or the merchant. In various embodiments, the user may berequired to select the transaction processing flow type duringinitiating or processing the transaction.

However, in other embodiments, the merchant may also select thetransaction processing flow type and request payment from the user. Ifthe user and/or the merchant (or other entity) is acting fraudulently,fraud analysis application 140 may flag the account as abusive ofpotentially abusive of a specific type of transaction processing flow.Thus, during future transaction processing, the account flag may beutilized to determine that the account previously abused a certaintransaction processing flow type by utilizing it incorrectly, and theflag may cause fraud analysis application 140 to select anothertransaction processing flow type even when the transaction processingflow type incorrectly abused by the account is selected (e.g.,automatically select a consumer flow over a personal flow). Such accountflag information may be utilized to automatically select the transactionprocessing flow type and/or enter input causing selection of thetransaction processing flow type. For example, where the merchant ispreviously flagged as acting abusively by requesting users select apersonal flow to avoid transaction fees but not provide consumerprotection, future users wish to process transactions with the merchantmay automatically be guided or placed in a commercial transactionprocessing flow when processing transactions with the merchant. Thus,the account flag may be used to cause selection of the transactionprocessing flow type by an entity wishing to interact with the flaggedaccount. Moreover, an administrator may perform review of flaggedaccounts to determine whether the flags are appropriate.

Transaction processing application 132 may correspond to one or moreprocesses to execute software modules and associated specializedhardware of transaction processor server 130 to provide payment servicesto merchants and users, for example though a account and/or paymentinstruments of the user to an account of the merchant. In this regard,transaction processing application 132 may correspond to specializedhardware and/or software to provide transaction processing and paymentservices through accounts, including digital wallets storing paymentinstruments. The services may allow for a payment to the merchant by auser through a payment instrument, including a credit/debit card,banking account, payment account with transaction processor server 130,and/or other funding instrument. In order to establish an account for amerchant and/or user to send and receive payments, transactionprocessing application 132 may receive information requestingestablishment of the payment account. The information may include userpersonal, business, and/or financial information. Additionally theinformation may include a login, account name, password, PIN, or otheraccount creation information. The merchant/user may provide a name,address, social security number, or other personal or businessinformation necessary to establish the account and/or effectuatepayments through the account. Transaction processing application 132 mayfurther allow the merchant/user to service and maintain the paymentaccount, for example, by adding and removing funding instruments.

Transaction processing application 132 may be used to provide a paymentfor a transaction to a merchant, for example, between communicationdevice 110 and merchant device 120. The payment for a transaction may beeffectuated through a plurality of different transaction processing flowtypes, such as a transaction processing flow type for personaltransaction or “friends and family” transactions that occur betweenknown users, such as if the user knows and trusts the other user. Such atransaction flow may also be utilized for payments between acquaintancesand/or transfers, and may be free for use but not provide consumerprotection. The transaction processing flow types may also include acommercial transaction flow for use in processing commercialtransactions or “goods and services” transactions between entitiesdesiring consumer protection for sales transactions, which may require afee for use. Selection of the transaction processing flow type may beautomatically entered by fraud protection application 140, and may, incertain embodiments, be changed through an interface output bytransaction processing application 132. Once a transaction processingflow is entered, transaction processing application 132 may process thetransaction in accordance with the services, processes, and features ofthe selected transaction processing flow. Transaction processingapplication 132 may debit an account of the user and provide the paymentto an account of the merchant. Transaction processing application 132may also be used to provide transaction histories for processedtransactions.

In various embodiments, transaction processor server 130 includes otherapplications 134 as may be desired in particular embodiments to providefeatures to transaction processor server 130. For example, otherapplications 134 may include security applications for implementingserver-side security features, programmatic client applications forinterfacing with appropriate application programming interfaces (APIs)over network 150, or other types of applications. Other applications 134may contain software programs, executable by a processor, including agraphical user interface (GUI), configured to provide an interface tothe user when accessing transaction processor server 130, where the useror other users may interact with the GUI to more easily view andcommunicate information. In various embodiments, other applications 134may include connection and/or communication applications, which may beutilized to communicate information to over network 150.

Additionally, transaction processor server 130 includes database 136. Aspreviously discussed, the user and/or the merchant may establish one ormore digital wallets and/or accounts with transaction processor server130. Digital wallets and/or accounts in database 136 may include userinformation, such as name, address, birthdate, paymentinstruments/funding sources, additional user financial information, userpreferences, and/or other desired user data. Users may link to theirrespective digital wallets and/or payment accounts through an account,user, merchant, and/or device identifier. Thus, when an identifier istransmitted to transaction processor server 130, e.g., fromcommunication device 110, one or more digital wallets and/or paymentaccounts belonging to the users may be found. Database 136 may alsostore the user preferences for an account for the user and/or merchant.

In various embodiments, transaction processor server 130 includes atleast one network interface component 138 adapted to communicatecommunication device 110 and/or merchant device 120 over network 150. Invarious embodiments, network interface component 138 may comprise a DSL(e.g., Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency (RF), andinfrared (IR) communication devices.

Network 150 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 150 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 150 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2A is an exemplary selection interface for choosing a particulartransaction processing flow type for use in transaction processing,according to an embodiment. Environment 200 a includes a communicationdevice 110 corresponding generally to the described features, processes,and components of communication device 110 in environment 100 of FIG. 1.In this regard, a user utilizing a communication device may viewinterface options 1000 on the communication device, where interfaceoptions 1000 corresponds to an interface of an application, such asservice provider application 112 of communication device 110 inenvironment 100 of FIG. 1.

In this regard, interface options 1000 display various transactionprocessing flow types that may be selected by users, merchants, and/orother entities during transaction processing to process a transactionutilizing certain features, services, and/or processes provided by aservice provider. For example, a personal transaction processing flowmay be selected through a personal option 1002 in interface options1000. Selection of personal option 1002 may initiate a transactionprocessing flow that provides transaction processing services betweenknown users, such as friends or family. Such a transaction processingflow may provide free transaction processing, but may not provideconsumer protection. In contrast, a sales option 1004, a payment requestoption 1008, and an invoice option 1010 may each provide commercialtransaction processing for sales or other commercial transactionsbetween entities. Such a transaction processing flow for commercialtransactions associated with sales option 1004, payment request option1008, and invoice option 1010 may require a fee to process atransaction, which may be paid by the buyer or deducted from payment tothe seller, but may provide consumer protection. For example, interfaceoptions 1000 display a notification 1012 that alerts entities of arequired fee 1014 as well as protection services 1016 to buyers and/orsellers.

FIG. 2B is an exemplary transaction processing interface for entry oftransaction information used in a risk analysis of selection of aparticular transaction processing flow type, according to an embodiment.Environment 200 b includes a communication device correspondinggenerally to the described features, processes, and components ofcommunication device 110 in environment 100 of FIG. 1. In this regard, auser utilizing the communication device may view an interface 1100 onthe communication device, where interface 1100 corresponds to aninterface of an application, such as service provider application 112 ofcommunication device 110 in environment 100 of FIG. 1.

In this regard, interface 1100 displays a transaction processing menu1102 for a transaction processing flow that allows an entity, such as auser, to engage in transaction processing for a transaction using a typeof transaction processing flow accessible through transaction processingmenu 1102. For example, transaction processing menu includes a recipientfield 1104 that allows the entity wishing to engage in transactionprocessing using transaction processing menu 1102 to enter recipientinformation for a payment or the other entity involved in thetransaction processing. Additionally, a contact list 1106 may allow theentity to quickly select from previous or known other entities toinitiate a transaction processing request and provide a payment to sucha contact. While viewing interface 1100, the entity may make a changeand/or selection of a transaction processing flow by selecting apersonal option 1108, a payment request option 1110, and/or an invoiceoption 1112. Selection of such an option may notify the service providerthat the entity wishes to utilize a specific transaction processingflow. Based on processing the transaction information and/or the accountinformation for the entities, the service provider may determine whetherone or more of the entities are acting fraudulently in the transactionprocessing and flag one or more of their accounts as abusive.

FIG. 2C is an exemplary transaction processing interface after entry ofinput to the transaction processing flow, according to an embodiment.Environment 200 c includes a communication device 110 correspondinggenerally to the described features, processes, and components ofcommunication device 110 in environment 100 of FIG. 1. In this regard, auser utilizing communication device 110 may view an interface 1200 oncommunication device 110, where interface 1100 corresponds to aninterface of a payment processing application, such as service providerapplication 112 of communication device 110 in environment 100 of FIG.1.

In this regard, interface 1200 displays a payment menu 1202 for entry ofinput to enter transaction and/or payment information and enter atransaction processing flow. For example, based on selection of arecipient entity in FIG. 2B, recipient information 1204 may be populatedin payment menu 1204. An entity utilizing payment menu 1202 may providea value 1206 for processing, as well as enter a message into messagefield 1208. Utilizing information, such as transaction informationincluding value 1206 and message field 1208 and account information, atransaction type may be determined by a service provider providinginterface 1200. The service provider may utilize the transaction type todetermine a transaction processing flow type required or suggested forprocessing the transaction type. In this regard, the service providermay automatically select the transaction processing flow type, forexample, by adding or not adding input to box 1210. Information 1212informs the buyer of the features and processes provided by selecting orunselecting box 1210 and entering into a transaction processing flow.Thus, if box 1210 is unselected, a personal transaction flow may beentered that does not include a fee but also does not provide purchaseor consumer protection. However, selection of box 1210 allows forconsumer protection but requires a fee. Thus, since box 1210 isunselected, a process for personal transaction processing is performedor canceled based on selection of navigation field 1214.

FIG. 3 is an exemplary system environment showing a database of aservice provider having data used to provide risk analysis and frauddetection during transaction processing, according to an embodiment.FIG. 3 includes transaction processor server 130 discussed in referenceto environment 100 of FIG. 1.

Transaction processor server 130 includes a database 136 having the datastored from one or more processing applications, such as those discussedin reference to environment 100 of FIG. 1. In this regard, database 136includes data sufficient for a service provider, such as transactionprocessor server 130, to determine a transaction type for a transactionto be processed by the service provider, and further determine atransaction processing flow required or suggested to process thetransaction.

For example, database 136 includes account data 2000 for one or moreaccounts held by the entities in the transaction. Thus, an entity mayutilize account A 2002 to process one or more transactions. Account A2002 includes past transactions 2004 processed by the account, which maybe used to determine whether the account is engaging in a personaltransaction between known users or a commercial transaction based onsimilar commercial transactions and/or with unknown users. In similarfashion, account interactions 2006 may be utilized to determine similarinformation based on interacting accounts with account A 2002. Accountinformation 2008 may include entity information and/or financialinformation for use in determining the transaction type with anotheraccount, such as account B 2012. Moreover, account A 2002 may be flaggedas an abuser of a particular type of transaction processing flow basedon abuser flag 2010. Thus, an account interacting with account A 2002,such as account B 2012 may include past transactions, 2014, accountinteractions 2016, and/or account information 2018 utilized to determinea transaction type for a transaction with account A 2002 and atransaction processing flow type for processing the transaction withaccount A 2002.

Database 136 may further include transaction data 2020 for a transactionto be processed between account A 2002 and account B 2012. Transactiondata 2020 may further be utilized by a service provider, such astransaction processor server 130, to determine a transaction type andassociated transaction processing flow type. For example, transactiondata 2020 may include an amount 2022 for the transaction, items 2024 inthe transactions, and entities 2026 (e.g., an entity A 2028 associatedwith account A 2002 and an entity B 2030 associated with account 2012)involved in the transaction. Additionally, transaction data 2020 mayinclude notes 2032, which may be processed to determine key words,terms, or phrases that indicate a transaction type. Moreover, shipping2034 may indicate shipping information of one or more entities that mayfurther be used to determine a transaction type.

FIG. 4 is a flowchart of an exemplary process for risk analysis andfraud detection for electronic transaction processing flows, accordingto an embodiment. Note that one or more steps, processes, and methodsdescribed herein may be omitted, performed in a different sequence, orcombined as desired or appropriate.

At step 402, a request to enter a transaction processing flow by a firstentity with a second entity is received, wherein the request comprisestransaction information for a transaction between the first entity andthe second entity. The transaction information may comprise at least oneof an amount for the transaction, at least one item in the transaction,data in a note field associated with the transaction, parties to thetransaction, or shipping information for the transaction.

At step 404, account data for a first account of the first entity and asecond account of the second entity is retrieved, for example, accessedfrom a database. The account data for the first account and the secondaccount may comprise at least one abuser flag for at least one of thefirst entity or the second entity. The at least one abuser flag may flagor identify the at least one of the first entity or the second entity asan abuser if the at least one of the first entity or the second entitypreviously fraudulently used a transaction processing flow type for thetransaction processing flow that did not require a fee for use of thetransaction processing flow type. The account data may comprise at leastone of a name for the first entity or the second entity, an address forthe first entity or the second entity, an entity type for the firstentity or the second entity, a shared entity status for the first entityand the second entity, previously account interactions for the firstaccount and the second account, amount of sent or received payments forthe first account or the second account, or number of other accountsinteracting with the first account or the second account.

A transaction type of the transaction is determined using the accountdata and the transaction information, at step 406. The transaction typemay be determined based on a transaction amount, an item in thetransaction, an address for the transaction, an account history for thefirst account and the second account, or a message associated with thetransaction. At step 408, input is automatically entered to thetransaction processing flow for the first entity based on thetransaction type, for example by automatically selecting a transactionprocessing flow type for use by the first entity based on thetransaction type. The input may be entered to a graphical user interfaceas a selection of an option within a field of the graphical userinterface. The graphical user interface may be displayed from a webpagefor a payment provider service associated with the transactionprocessing flow or dedicated application for the payment providerservice. Thus, the input may comprise a selection of a transactionprocessing flow type for the transaction processing flow to process thetransaction based on the transaction type. The input may thereforepre-select one of a merchant transaction processing flow type or apersonal transaction processing flow type. The input may automaticallyselect a transaction processing flow type having no fee for use of thetransaction processing flow type when only the first account and thesecond account previously interacted.

In various embodiments, the selection of the transaction processing flowtype comprises a merchant sale flow for processing the transaction,wherein merchant sale flow requires a fee for use of the merchant saleflow to process the transaction. In other embodiments, the selection ofthe transaction processing flow type comprises a personal transfer flowfor processing the transaction, wherein the personal transfer flow doesnot require a fee for use of the friends and family transfer flow. Thus,the selection of the transaction processing flow type determines atleast one of fees for the transaction, buyer protection for thetransaction, insurance for a payment or an item in the transaction, orreimbursement procedures for fraud in the transaction. Moreover, anoption may be provided to the first entity, wherein the option allowsthe first entity to change the input to the transaction processing flow.Thus, a change to the input in the selectable field by the first entitymay be received, wherein a selection of a transaction processing flowtype for the transaction processing flow is changed based on the changeto the input. In response to receiving the change, information may beprovided to the first entity about a previously selected transactionprocessing flow type, and wherein the information comprises availablefeatures and unavailable features for the previously selectedtransaction processing flow type.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the communication device may comprise a personal computingdevice (e.g., smart phone, a computing tablet, a personal computer,laptop, a wearable computing device such as glasses or a watch,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The service provider may utilize a network computing device(e.g., a network server) capable of communicating with the network. Itshould be appreciated that each of the devices utilized by users andservice providers may be implemented as computer system 500 in a manneras follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 150. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A system comprising: a non-transitory memorystoring account data for a first account of a first entity and a secondaccount of a second entity; and one or more hardware processorsconfigured to execute instructions to cause the system to performoperations comprising: receiving a request to enter a transactionprocessing flow by a first entity with a second entity, wherein therequest comprises transaction information for a transaction between thefirst entity and the second entity; accessing the account data for thefirst account of the first entity and the second account of the secondentity; determining a transaction type of the transaction using theaccount data and the transaction information; and automatically enteringdata to the transaction processing flow for the first entity based onthe transaction type.
 2. The system of claim 1, wherein the data isentered to a graphical user interface as a selection of an option withina field of the graphical user interface.
 3. The system of claim 2,wherein the graphical user interface is displayed one of a webpage for apayment provider service associated with the transaction processing flowor dedicated application for the payment provider service.
 4. The systemof claim 1, wherein the data comprises a selection of a transactionprocessing flow type for the transaction processing flow to process thetransaction based on the transaction type.
 5. The system of claim 4,wherein the selection of the transaction processing flow type comprisesa merchant sale flow for processing the transaction, and whereinmerchant sale flow requires a fee for use of the merchant sale flow toprocess the transaction.
 6. The system of claim 4, wherein the selectionof the transaction processing flow type comprises a personal transferflow for processing the transaction, and wherein the personal transferflow does not require a fee for use of the personal transfer flow. 7.The system of claim 4, wherein the selection of the transactionprocessing flow type determines at least one of fees for thetransaction, buyer protection for the transaction, insurance for apayment or an item in the transaction, or reimbursement procedures forfraud in the transaction.
 8. The system of claim 1, wherein theoperations further comprising: providing an option to the first entity,wherein the option allows the first entity to change the data to thetransaction processing flow.
 9. The system of claim 8, wherein theoption comprises a selectable field within an interface, and wherein theoperations further comprise: receiving a change to the data in theselectable field by the first entity, wherein a selection of atransaction processing flow type for the transaction processing flow ischanged based on the change to the data.
 10. The system of claim 9,wherein the operations further comprise: in response to receiving thechange, providing information to the first entity about a previouslyselected transaction processing flow type, and wherein the informationcomprises available features and unavailable features for the previouslyselected transaction processing flow type.
 11. A method comprising:receiving a request to enter a transaction processing flow by a firstentity with a second entity, wherein the request comprises transactioninformation for a transaction between the first entity and the secondentity; retrieving account data for a first account of the first entityand a second account of the second entity; determining a transactiontype of the transaction using the account data and the transactioninformation; and selecting a transaction processing flow type for use bythe first entity based on the transaction type.
 12. The method of claim11, wherein the account data for the first account and the secondaccount comprises at least one abuser flag for at least one of the firstentity or the second entity.
 13. The method of claim 12, wherein the atleast one abuser flag identifies the at least one of the first entity orthe second entity as an abuser if the at least one of the first entityor the second entity previously fraudulently used a transactionprocessing flow type for the transaction processing flow that did notrequire a fee for use of the transaction processing flow type.
 14. Themethod of claim 11, wherein the transaction information comprises atleast one of an amount for the transaction, at least one item in thetransaction, data in a note field associated with the transaction, orshipping information for the transaction.
 15. The method of claim 11,wherein the account data comprises at least one of a name for the firstentity or the second entity, an address for the first entity or thesecond entity, an entity type for the first entity or the second entity,a shared entity status for the first entity and the second entity,previously account interactions for the first account and the secondaccount, amount of sent or received payments for the first account orthe second account, or number of other accounts interacting with thefirst account or the second account.
 16. The method of claim 11, whereinthe selecting the transaction processing flow type comprisesautomatically pre-selecting one of a merchant transaction processingflow type or a personal transaction processing flow type.
 17. The methodof claim 11, further comprising: providing an option to change thetransaction processing flow type, wherein selection of the optionrequires confirmation of the selection by the first entity.
 18. Themethod of claim 11, wherein the input automatically selects atransaction processing flow type having no fee for use of thetransaction processing flow type when only the first account and thesecond account previously interact.
 19. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a machine to perform operationscomprising: receiving a request to enter a transaction processing flowby a first entity with a second entity, wherein the request comprisestransaction information for a transaction between the first entity andthe second entity; retrieving account data for a first account of thefirst entity and a second account of the second entity; determining atransaction type of the transaction using the account data and thetransaction information; and automatically entering data to thetransaction processing flow for the first entity based on thetransaction type.
 20. The non-transitory machine-readable medium ofclaim 19, wherein the transaction type is determined based on atransaction amount, an item in the transaction, an address for thetransaction, an account history for the first account and the secondaccount, or a message associated with the transaction.